Chrome has locked the profile

[zaer73]

Is there an existing issue for this?

• I have searched the existing issues.

Is this a problem caused by your code, or is it specifically because of the library?

• I have double-checked my code carefully.

Describe the bug.

Initialize error: Failed to launch the browser process!
[29:29:0214/174332.818614:ERROR:process_singleton_posix.cc(358)] The profile appears to be in use by another Google Chrome process (30) on another computer (f524cfce0217). Chrome has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chrome.
[29:29:0214/174332.818714:ERROR:message_box_dialog.cc(190)] Unable to show message box: Google Chrome - The profile appears to be in use by another Google Chrome process (30) on another computer (f524cfce0217). Chrome has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chrome.

Expected Behavior

.

Steps to Reproduce the Bug or Issue

.

WhatsApp Account Type

Standard

Browser Type

chrome

Operation System Type

linux

Phone OS Type

android

WhatsApp-Web.js Version

last

WhatsApp Web Version

last

Node.js Version

18

Authentication Strategy

LocalAuth

Additional Context

No response

[rseiffert]

UPDATE START
Sorry, my own fault. Somehow the node.js app started twice (arghhh)
UPDATE END

Same here, since yesterday (2025/02/14) without updating the package.
It starts up normally, but as soon as I make a change to my source code and nodemon kicks in, the error occurs.

Error: Failed to launch the browser process!
[40410:259:0215/083634.114568:ERROR:process_singleton_posix.cc(340)] Failed to create /Users/.../projects/play/server/.wwebjs_auth/session/SingletonLock: File exists (17)
[40410:259:0215/083634.114854:ERROR:chrome_main_delegate.cc(557)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption.

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

    at onClose (/Users/.../projects/play/server/node_modules/.pnpm/puppeteer-core@18.2.1_bufferutil@4.0.8/node_modules/puppeteer-core/src/node/BrowserRunner.ts:327:9)
    at ChildProcess.<anonymous> (/Users/rudigerseiffert/projects/play/server/node_modules/.pnpm/puppeteer-core@18.2.1_bufferutil@4.0.8/node_modules/puppeteer-core/src/node/BrowserRunner.ts:316:16)
    at ChildProcess.emit (node:events:519:35)
    at ChildProcess.emit (node:domain:489:12)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:294:12)
```

[zaer73]

Apparently, this problem occurs when you have enabled the WhatsApp Web app lock feature.

[jjr-dev]

this should solve it, before starting the connection

export const clearProfileLock = async (id) => {
    try {
        const lockFilePath = ClientHelper.base_path + `/${ClientHelper.session_prefix}-${id}/SingletonLock`;

        const stats = fs.lstatSync(lockFilePath);

        if (stats.isSymbolicLink()) {
            fs.unlinkSync(lockFilePath);
        }
    } catch (err) {
        console.log(`Clear profile lock error: ${err}`);
    }
};